View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001257 | T99X171.00 SKB Eagle | SW Issue | public | 2021-05-31 09:28 | 2021-09-30 10:36 |
| Reporter | (ALTech) Younkwang Jung | Assigned To | (ALTech) Younkwang Jung | Due Date | |
| Priority | normal | Severity | s2-severe | Reproducibility | have not tried |
| Status | closed | Resolution | not fixable | ||
| Summary | 0001257: [Smart3][BTF] Tombstone file created during Monkey test ( com.android.bluetooth ) | ||||
| Description | Hi Kerwin During the Monkey test, sometimes a tombstone file is generated on Bluetooth. [MonkeyTest Command] monkey -p com.skb.tv -p com.skb.senior -p com.skb.zemkids -p com.google.android.youtube.tv --ignore-crashes --ignore-timeouts --throttle 1000 --pct-touch 0 --pct-motion 0 --pct-trackball 0 --pct-nav 40 --pct-syskeys 0 --pct-majornav 40 -v 9000000 & I attached the Tombstone file and logcat information, so please check it. There seems to be no operational issue. Thanks YK.Jung | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) SY Yoon , |
|---|
|
|
|
|
|
Hi Mr. YK Jung, In tombstone file, Bluetooth process was died due to native crash. Below is addr2line result of some program counters #00 pc 0005ec56 /apex/com.android.runtime/lib/bionic/libc.so (abort+166) (BuildId: a82a8324059a3f30a292a0e928691aca) ==> abort() in libc #01 pc 0018138f /system/lib/libbluetooth.so (hci_timeout_abort(void*)+30) (BuildId: 49666282d831c1cd61711a97d7bc5de9) ==> system/bt/hci/src/hci_layer.cc:445 #02 pc 0021297f /system/lib/libbluetooth.so (alarm_ready_generic(alarm_t*, std::__1::unique_lock<std::__1::mutex>&)+326) (BuildId: 49666282d831c1cd61711a97d7bc5de9) ==> system/bt/osi/src/alarm.cc:600 The last message before Bluetooth died was 05-30 02:30:39.797 4017 4523 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet It looks like application asking BT stack to stop scanning for BT devices so I think the command to BT controller was stuck somehow. But I have no idea why there is a command timeout at the point. The stop scanning event was similar with others ... 05-30 01:35:26.849 4017 4523 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet 05-30 01:35:26.858 4017 4523 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet 05-30 01:35:27.068 4017 4101 D bt_btif_config: btif_get_device_type: Device [a4:97:b1:40:1c:13] type 1 05-30 01:35:28.969 4017 4101 D bt_btif_config: btif_get_device_type: Device [00:09:74:00:2d:2e] type 3 05-30 01:35:29.356 4017 4101 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:00:9a] type 3 05-30 01:35:29.834 4017 4101 D bt_btif_config: btif_get_device_type: Device [00:09:74:00:2d:60] type 3 05-30 01:35:34.204 4017 4101 D bt_btif_config: btif_get_device_type: Device [40:5b:d8:6d:13:62] type 1 05-30 01:35:34.456 4017 4101 D bt_btif_config: btif_get_device_type: Device [40:19:20:10:00:3d] type 3 05-30 01:35:34.492 4017 4101 D bt_btif_config: btif_get_device_type: Device [00:09:74:00:2d:49] type 3 .... 05-30 02:09:57.975 4017 4523 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet 05-30 02:09:57.995 4017 4101 D bt_btif_config: btif_get_device_type: Device [40:19:20:60:01:2e] type 3 05-30 02:09:58.106 4017 4101 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:be:12] type 1 05-30 02:09:58.234 4017 4101 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:be:6c] type 1 05-30 02:09:58.256 4017 4101 D bt_btif_config: btif_get_device_type: Device [ec:5c:68:1d:bd:e2] type 1 .... |
|
|
Hi Kerwin Then should you ask Amlogic for help to solve this issue? Or should you add debugging information to trace the issue? How can we solve this issue? Please give me your opinion. SKB will discuss this BT side issue if the field urgent issues are resolved. ( hdmi/rcu/ota/video issue.. ) I think we should prepare for this issue as well. Thank you YK.Jung |
|
|
Hi Jacky Chiang, Could you provide any action items to debug this issue ? And if there are some action items that ALT should do, please let me know. |
|
|
Hi Mr. SY Yoon and YK Jung, Before Bluetooth native process crashed, system seems had some problem and started to kill background process. I think it is hard to distinguish whether the root cause is in Bluetooth stack. Please check logs below =============== logcat.log.0114 =========== ... 05-30 02:19:38.813 3463 3463 I Zygote : Process 24800 exited due to signal 9 (Killed) 05-30 02:19:38.813 3832 4277 I ActivityManager: Process com.google.android.tv:common (pid 24800) has died: cch+65 CEM ... 05-30 02:19:38.861 3463 3463 I Zygote : Process 26618 exited due to signal 9 (Killed) ... 05-30 02:19:38.946 3832 4278 I ActivityManager: Process android.process.media (pid 26618) has died: cch+25 CEM ... 05-30 02:19:39.024 3463 3463 I Zygote : Process 24685 exited due to signal 9 (Killed) 05-30 02:19:39.025 3832 6957 I ActivityManager: Process com.google.android.tv (pid 24685) has died: cch+15 CEM ... Killed) 05-30 02:19:39.332 3832 6957 I ActivityManager: Process com.vasott.iset (pid 1478) has died: svcb SVC 05-30 02:19:39.335 3832 6957 W ActivityManager: Scheduling restart of crashed service com.vasott.iset/.iSetService in 1000ms 05-30 02:19:39.336 3463 3463 I Zygote : Process 4283 exited due to signal 9 (Killed) 05-30 02:19:39.336 3832 3863 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 1478 in 0ms 05-30 02:19:39.367 3832 5481 I ActivityManager: Process com.vasott.leanbacklauncher.partnercustomizer (pid 4283) has died: svcb SVC 05-30 02:19:39.369 3832 5481 W ActivityManager: Scheduling restart of crashed service com.vasott.leanbacklauncher.partnercustomizer/.CheckUsbService in 10967ms 05-30 02:19:39.369 3832 3863 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4283 in 0ms 05-30 02:19:39.403 3463 3463 I Zygote : Process 24723 exited due to signal 9 (Killed) 05-30 02:19:39.433 15094 15094 W TvSearchApp: onTrimMemory level=15 05-30 02:19:39.436 2457 2457 W TvSearchApp: onTrimMemory level=15 05-30 02:19:39.442 3832 6957 I ActivityManager: Process com.google.process.gservices (pid 24723) has died: prev LAST 05-30 02:19:39.443 3832 3863 I libprocessgroup: Successfully killed process cgroup uid 10040 pid 24723 in 0ms 05-30 02:19:39.469 3463 3463 I Zygote : Process 31298 exited due to signal 9 (Killed) 05-30 02:19:39.472 3463 3463 I Zygote : Process 24712 exited due to signal 9 (Killed) 05-30 02:19:39.484 3463 3463 I Zygote : Process 4494 exited due to signal 9 (Killed) 05-30 02:19:39.491 3832 5481 I ActivityManager: Process com.google.android.gms.unstable (pid 31298) has died: cch+35 CEM 05-30 02:19:39.492 3832 3863 I libprocessgroup: Successfully killed process cgroup uid 10040 pid 31298 in 0ms 05-30 02:19:39.495 3463 3463 I Zygote : Process 24965 exited due to signal 9 (Killed) 05-30 02:19:39.496 3463 3463 I Zygote : Process 4350 exited due to signal 9 (Killed) ... 05-30 02:19:39.562 3463 3463 I Zygote : Process 31745 exited due to signal 9 (Killed) 05-30 02:19:39.577 3523 3523 W lowmemorykiller: Failed to open /proc/4429/oom_score_adj; errno=2: process 4429 might have been killed ... 05-30 02:19:39.578 3832 20590 I ActivityManager: Process com.google.android.tvrecommendations (pid 24965) has died: prcl BFGS 05-30 02:19:39.578 3832 3863 I libprocessgroup: Successfully killed process cgroup uid 10044 pid 24965 in 0ms 05-30 02:19:39.579 3832 20590 W ActivityManager: Scheduling restart of crashed service com.google.android.tvrecommendations/.NotificationsService in 30757ms 05-30 02:19:39.611 3832 18326 I ActivityManager: Process com.tvstorm.tv.ime (pid 4350) has died: svcb SVC 05-30 02:19:39.612 3832 3863 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4350 in 0ms ... 05-30 02:30:39.797 4017 4523 W bt_btm_ble: btm_ble_process_adv_pkt_cont device no longer discoverable, discarding advertising packet 05-30 02:30:39.902 3626 3626 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_05 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Bluetooth native process crash ^^^^^^^^^^^^^ ... |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-05-31 09:28 | (ALTech) Younkwang Jung | New Issue | |
| 2021-05-31 09:28 | (ALTech) Younkwang Jung | Status | new => assigned |
| 2021-05-31 09:28 | (ALTech) Younkwang Jung | Assigned To | => (SW) Kerwin Chen |
| 2021-05-31 09:28 | (ALTech) Younkwang Jung | File Added: logcat.log.0114.zip | |
| 2021-05-31 09:28 | (ALTech) Younkwang Jung | File Added: tombstone_05 | |
| 2021-05-31 09:28 | (ALTech) Younkwang Jung | Issue Monitored: (SW) Brent Choi | |
| 2021-05-31 09:29 | (ALTech) Younkwang Jung | Issue Monitored: (SW) Jerry Lin | |
| 2021-05-31 09:29 | (ALTech) Younkwang Jung | Issue Monitored: (ALTech) SY Yoon | |
| 2021-06-01 08:41 | (SW) Kerwin Chen | Note Added: 0007309 | |
| 2021-06-01 08:42 | (SW) Kerwin Chen | Assigned To | (SW) Kerwin Chen => (ALTech) Younkwang Jung |
| 2021-06-01 08:42 | (SW) Kerwin Chen | Status | assigned => acknowledged |
| 2021-06-01 09:37 | (ALTech) Younkwang Jung | Note Added: 0007312 | |
| 2021-06-01 10:48 | (ALTech) SY Yoon | Issue Monitored: (SW) Jacky Chiang | |
| 2021-06-01 10:53 | (ALTech) SY Yoon | Note Added: 0007314 | |
| 2021-06-02 10:27 | (SW) Kerwin Chen | Note Added: 0007332 | |
| 2021-09-30 10:36 | (ALTech) Younkwang Jung | Status | acknowledged => closed |
| 2021-09-30 10:36 | (ALTech) Younkwang Jung | Resolution | open => not fixable |
